|
|
|
|
|
|
|
|
|
|
- Overview
- Checking the elements installed on the Linux server
- Installing WEBDEV Application Server for Linux
- Checking the Application Server setup
- Checking the Apache server
- Running the test from a Windows browser
- Testing the remote administrator
- Increase the number of simultaneous authorized connections
- Number of semaphores
- Number of segments of shared memory
- Minimum size of the shared memory
Install a WEBDEV Application Server for Linux
There are several steps to install the WEBDEV Application Server on a 64-bit Linux server: - Checking the elements installed on the Linux server.
- Installation of WEBDEV Application Server 64-bit for Linux.
- Checking the Application Server setup.
- Configuring the users and their rights for deploying WEBDEV applications.
Note: Only a 64-bit version can be installed. Checking the elements installed on the Linux server To work properly, the WEBDEV Application Server for Linux requires: - the presence of Apache server. This HTTP server must work properly. To check it is working, simply start a Web explorer from another computer and enter the following address: "http://<Server name>".
Note: to install the WEBDEV Application Server for Linux, you must know:- the name and path of configuration file for the Apache server (/etc/httpd/conf/http.conf for example).
- the name and path of the script used to reload the Apache configuration (/usr/sbin/apachectl -k graceful for example).
- the optional presence of an FTP server (managing the connections with password).
- the presence of the libstdc++ library (libstdc++-libc6.2-2.so.3 library).
Note: if a program locks the use of this library, then this program must be disabled. - the presence of the QT 4.5 library (or later). This library is required to use the drawings in Linux.
Checking these elements must be done before installing WEBDEV for Linux. In Appendix 2: Checking the server, you will find the steps to check the most common Linux distributions. Installing WEBDEV Application Server for Linux To install WEBDEV Application Server for Linux, you can: - run "WEBDEV_Install64" on the Linux server from the installation package.
- copy the content of the installation package to the Linux server and run "WEBDEV_Install".
Note: execution rights are required to run this program, otherwise the message "Permission not granted" appears. The following line allows you to grant execution rights: chmod +x WEBDEV_Install64 The main setup steps are: - Select the installation language. By default, the window is displayed in the language of the computer.
- Accept the license agreement:
To validate this screen, you must scroll through the entire license agreement with the up/down arrows. - Check the requirements:
- Specify whether the replication server is to be installed:
- Enter the activation key.
- Select the installation directory:
We advise you to keep the suggested directory. - Specify the parameters to install the WEBDEV Application Server for Linux:
- the path of the Apache configuration file. To get the name and path of this file, see Appendix 2: Checking the server.
If the specified path is not correct, an error message appears. - the command line used to reload the Apache configuration once an alias has been added (this operation is automatically performed when the WEBDEV websites are installed by FTP).
- the possibility of allowing the deployment of sites from previous versions.
- Specify the name of the Unix group corresponding to the administrator group of WEBDEV Application Server. The group proposed by default is webdevadmin.
The group is automatically created if it does not exist. - Also specify the name and password of the first deployment account. This account is the User account used to log in to the administration sites. it is also used to deploy sites and web services. If this account doesn't exist, it will be created: in this case, make sure you retain the account's characteristics. If this account exists, the password specified in this screen will not be taken into account.
- Validate the setup of the application server.
- The setup is completed. The setup report is displayed.
Checking the Application Server setup Once the WEBDEV Application Server for Linux is installed, it is recommended to check the following points. Checking the Apache server This check must be performed if the setup was ended properly or if the setup ended with the "Config-broken" error. For more details on the different points to check, see Appendix 2: Checking the server. Running the test from a Windows browser To check whether the WEBDEV Application Server for Linux works properly: - Open an Internet browser.
- Enter the following address:
http://<Server IP address>/WD300AWP/WD300AWP/version
- The browser displays a few lines indicating the WEBDEV version that is installed. For example:
WEBDEV 30.0 Linux
Copyright © PC SOFT 1993-2023
WD300AWP 30.00Af VI:
WD300session 30.00Al VI:30-300052g
WD300admind 30.00Am VI:30-300052g
(TST) 1303667-1699876806-1394533-YM
Testing the remote administrator The remote administrator is the application used to manage the user accounts and the WEBDEV websites on the server. To check the operating mode of the remote administrator: - Open an Internet browser.
- Enter the following address:
http://<Server IP address>/WDAdminWeb
where "Server IP address" corresponds to the IP address of the Linux server.
Caution: this address is case sensitive (lowercase/uppercase characters). If a connection error occurs, forget to check the case and the spelling. - The administrator asks for identification. Enter the username and password specified when the WEBDEV Application Server was installed.
Problems that may be encountered while testing the administrator - Error 403 appears when the remote administrator is started:
Cause: The installed Apache version has a "deny from all" clause in its configuration file..
Solution:
Add a <Directory> clause just before the definition of ScriptAlias in the Apache configuration file:
<Directory "/usr/local/WEBDEV/30.0/AWP">
allow from all
</Directory>
ScriptAlias /WD300AWP/ "/usr/local/WEBDEV/30.0/AWP"
- The images are not displayed in the remote administrator:
If you retrieve the URL of the image that is not displayed properly ("Properties" in the image context menu) and test it in the browser, the error #403 is displayed.
Cause The _WEB alias has been defined for the Apache server, but an Apache option locks access to it.
Solution: For each alias directory, a <Directory> directive must be defined in the Apache configuration file.
If the remote administrator or the WEBDEV websites do not work properly We advise you to perform the following operations: - See the system "logs" (for example /var/log/messages). These files may contain information about the errors that occurred (especially errors about rights).
- Restart the application server. The following command can be used:
killall WD300admind
/etc/init.d/WEBDEV30 restart - Reboot the server if necessary.
Increase the number of simultaneous authorized connections The number of connections supported by the WEBDEV Application Server depends on the following system resources: - the number of semaphores.
- the number of segments of shared memory.
- the minimum size of shared memory.
Number of semaphores The WEBDEV Application Server uses a number of semaphores proportional to the maximum number of simultaneous authorized connections. To find out the maximum number of available semaphores, run the following command line: This command line returns a series of numbers, the last one corresponding to the number of current semaphores (250 32000 32 170 for example, corresponding to about 32 connections).
The number of semaphores required to manage n sessions is given by the following formula: s = 4 +4 * nFor example, to manage 100 simultaneous connections, the minimum number of semaphores required is: 4 + 4 * 100 = 404 To modify the number of semaphores: - Edit the /etc/sysctl.con file in a text editor. For example, the following command line allows you to edit a file:
Note: you can also edit the file with:
- Add or modify the line corresponding to the "kernel.sem" entry and specify the new setting:
kernel.sem = xxx xxxxx xx 404
where the Xs represent the digits that were previously returned. - To take these new parameters into account, use the following command line:
Number of segments of shared memory The number of segments of shared memory to manage n connections must be equal to 4 + n. To find out the number of segments of shared memory, run the following command line: /sbin/sysctl kernel.shmmni To modify the number of segments of shared memory: - Edit the /etc/sysctl.con file in a text editor.
For example, the following command line allows you to edit a file:
Note: you can also edit the file with:
- Add or modify the line corresponding to the "kernel.shmmni" entry and specify the new setting:
where xxx corresponds to the new setting. - To take these new parameters into account, use the following command line:
Minimum size of the shared memory The minimum size of shared memory must be calculated according to the number of connections. The calculation is as follows: (SHMHISTORYSIZE + (SHMDIALOGSIZE * n))*1024 where: - n is the number of simultaneous connections.
- SHMHISTORYSIZE corresponds to the size (in KB) of the history of WEBDEV sessions (2048 KB by default).
- SHMDIALOGSIZE corresponds to the size (in KB) of the maximum request sent to the server (500 KB by default.
SHMHISTORYSIZE and SHMDIALOGSIZE are defined in the WEBDEV configuration files. For more details, see Appendix 3: Configuration file.
To get the size of the shared memory, run the following command line: /sbin/sysctl kernel.shmmax : - Edit the /etc/sysctl.con file in a text editor. For example, the following command line allows you to edit a file:
Note: you can also edit the file with:
- Add or modify the line corresponding to the "kernel.shmmax" entry and specify the new setting:
where xxx corresponds to the new setting. - To take these new parameters into account, use the following command line:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|